MSF for Agile Software Development

Reviews

Review

 

Overview

A review item is used to define code reviews, design reviews, sprint planning reviews, sprint reviews or sprint retrospectives.  Review items can either be used to call for a review or to record the information from a review that has already happened.  Reviews are used to ensure quality through interaction between members of the team or between the team and the end-users.

Sprint Planning Meetings are used to plan the work for the upcoming sprint.  A review of type Sprint Planning is used to record this meeting. 

Sprint Review Meetings are used to discuss the progress of the sprint and to review the work product with the customer.  A review of type Sprint Review is used to record this meeting.

 

Sprint Retrospectives are used to record relevant information from the team’s retrospective meeting. 

Code and Design Reviews are used by the team to help ensure the quality of the application.  These reviews are called by individual developers or architects to ensure consistent coding and design practices. 

 

States and Transitions


New


A review is new when it is first created.  Create a new review when work has been identified from either the user stories or another source.


New to Active

 

Investigate

A review may be assigned to a team member for validation or analysis before it is assigned to a sprint.

Accepted

A review may be made active when it has been validated and assigned to a team member.


Active


A review is active when it has been reviewed by the scrum master and team and has been targeted for further analysis or has been accepted as valid work for the project.


Active to Closed

Overtaken

A review may be closed if the item has been overtaken by events in the project.

Duplicate

A review may be closed if the item is the duplicate of another review.

Postponed

A review may be closed if the project team decides to postpone the work.

Removed

A review may be closed if it has been removed from the project backlog.


Active to Resolved

Complete (No Verification)

A review may be marked as resolved once the work has been completed and may or may not need to be verified.

Complete (Requires Verification)

A review may be marked as resolved once the work has been completed and may or may not need to be verified.


Resolved


A review is resolved when the work that it specified has been completed but not yet tested or  reviewed.


Resolved to Active

Verification Failed

A review may need to be reactivated if verification of the work completed is not successful.


Resolved to Closed

Verified

A review may be closed once the work completed has been successfully verified.


Closed


A review is closed when the work that it specifies has either been completed or is no longer needed for the the project.


Closed to Active

Reactivated

A review may need to be reactivated for a variety of reasons.

Closed in Error

A review may have been closed by accident and need to be reopened.


Fields

Title

Required. The title provides a concise description of the review. The title should be descriptive enough to allow the team to understand what the potential review is.

Area

The area is used to group the review into an appropriate feature or team area. The area must be a valid node in the project hierarchy.

Type

The type of review being conducted.  Review types are Sprint Planning, Sprint Review, Sprint Retrospective, Code or Design.

Sprint

The iteration in which the review could be occur.

Called By

The person calling for the review.

Called Date

The date the review was requested.

Assigned To

The current person that review is assigned to. Generally, it is a scrum master but may be any of the project team members.

State

Required.  Used to determine the status of the review in its lifecycle.  A review can be in the New,  Active, Resolved or Closed states.

Reason

The reason a review is in the current state.

Purpose

The stated purpose of the review.

Minutes

The minutes of the review meeting.

Comments

Comments collected during the review or review meeting.

History

The history field contains the set of changes to the work item.

Links

Links to related work items, hyperlinks, changesets, or source code files.

Attachments

Attach related files providing additional documentation around the review.

     

© 2007 TFS MVP Community

MVP Logo

Version 2.1